-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Fix span issues in object safety suggestions #98506
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix span issues in object safety suggestions #98506
Conversation
r? @oli-obk (rust-highfive has picked a reviewer for you, use r? to override) |
= help: consider moving `f` to another trait | ||
= help: consider moving `f2` to another trait |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a bit non-ideal, we shouldn't be suggesting to move functions from the supertrait, since the supertrait is not local. But it's a bit unrelated to this fix.
@bors r+ rollup |
📌 Commit eff865c has been approved by |
…askrgr Rollup of 9 pull requests Successful merges: - rust-lang#98331 (Fix rustdoc argument error) - rust-lang#98506 (Fix span issues in object safety suggestions) - rust-lang#98563 (interpret: refactor allocation info query) - rust-lang#98576 (small regions refactoring) - rust-lang#98577 (Fix "kind" for associated types in trait implementations in rustdoc JSON) - rust-lang#98578 (Remove eddyb from miri failure pings) - rust-lang#98579 (liballoc tests: avoid int2ptr cast) - rust-lang#98581 (Add triagebot mentions.) - rust-lang#98587 (libcore tests: avoid int2ptr casts) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
Fixes #98500